Fix/usage timezone handling#3086
Conversation
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Reviewed by gpt-5.5-20260423 · 310,160 tokens |
|
Hi @IamCoder18 ! I hope you're doing well. I'm excited to let you know that I just released the new version of the Usage dashboard, and it includes a fix to ensure all dates are in UTC. I’d love to hear your thoughts about the new dashboard! Thanks for your collaboration! |
|
Hi! The usage dashboard actually isn't working for me. It doesn't show any data. 
But I'm sure that with the data loading issue fixed, the new usage dashboard would be great for tracking usage. |
If you could send me a direct message on Discord or an email with your account details, that would be awesome! I’d love to help you figure out what’s going on. Thanks! |
2 participants
Summary
Fix timezone handling in the usage tab so dates are grouped by the user's local timezone instead of UTC. This affects "By Day", "By Model & Day" views, streak calculation, and streak calendar.
Closes #3085
Changes:
/api/profile/usagenow acceptstimeZoneparameter and uses PostgreSQLAT TIME ZONEfor timezone-aware date groupingIntl.DateTimeFormat().resolvedOptions().timeZonetoLocaleDateString('en-CA', { timeZone })for correct local date formattingnullto defer query until browser timezone is detectedVisual Changes
N/A - functionality fix, dates now correctly reflect user's local timezone.
Reviewer Notes
en-CAlocale is used because it formats dates asYYYY-MM-DDby defaultisValidTimezone()function to validate IANA timezone strings and prevent SQL injection